✅ Deploy Preview for rslint ready!

Name	Link
🔨 Latest commit	33aa703
🔍 Latest deploy log	https://app.netlify.com/projects/rslint/deploys/694e730c1728a9000809bf87
😎 Deploy Preview	https://deploy-preview-422--rslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

🤖 This pull request has been linked to DevBird Task #2607

View the task details and manage the automated development workflow in DevBird.

Learn more about DevBird here or the announcement blog post here.

📋 DevBird Task Prompt

Objective

Implement the ban-ts-comment rule from typescript-eslint from scratch with complete test coverage.

Documentation & Resources

• Rule documentation: https://typescript-eslint.io/rules/ban-ts-comment/
• TypeScript-ESLint GitHub repository: https://github.com/typescript-eslint/typescript-eslint
• Original rule implementation: https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/src/rules/ban-ts-comment.ts
• Original test cases: https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/tests/rules/ban-ts-comment.test.ts
• TypeScript triple-slash directives: https://www.typescriptlang.org/docs/handbook/triple-slash-directives.html
• typescript-go AST documentation: https://github.com/microsoft/typescript-go

Rule Description

This rule disallows @ts- comments or requires descriptions after directive. TypeScript provides several directive comments that can be used to alter how the compiler treats the code. Using these comments to suppress TypeScript compiler errors reduces the effectiveness of TypeScript overall.

Scope

Create a complete implementation of the ban-ts-comment rule including:

1. Full rule implementation in Go at internal/rules/ban_ts_comment/ban_ts_comment.go
2. Comprehensive test suite at internal/rules/ban_ts_comment/ban_ts_comment_test.go
3. Copy ALL test cases from the original typescript-eslint test file
4. Enable the test in packages/rslint-test-tools/rstest.config.mts by uncommenting line 35

Technical Requirements

• Follow the existing rslint rule implementation pattern (see internal/rules/no_debugger/ for reference)
• Use typescript-go AST node types and traversal
• Implement proper error messages matching the original rule
• Support all configuration options from the original rule (allow directives, require descriptions, etc.)
• The rule should handle: @ts-expect-error, @ts-ignore, @ts-nocheck, @ts-check
• Register rule in the appropriate plugin registry

Implementation Pattern

package ban_ts_comment

import (
    "github.com/microsoft/typescript-go/shim/ast"
    "github.com/web-infra-dev/rslint/internal/rule"
)

var BanTsCommentRule = rule.Rule{
    Name: "ban-ts-comment",
    Run: func(ctx rule.RuleContext, options any) rule.RuleListeners {
        // Implementation here
        return rule.RuleListeners{
            // AST node listeners
        }
    },
}

Test Requirements

• Copy ALL test cases from https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/tests/rules/ban-ts-comment.test.ts
• Adapt test cases to rslint's Go testing framework
• Include both valid and invalid test cases
• Test all configuration options
• Ensure tests pass before marking task complete

Success Criteria

• Rule implementation is complete and handles all edge cases
• All tests pass
• Test is enabled in packages/rslint-test-tools/rstest.config.mts
• Code follows existing rslint patterns and conventions
• Rule is properly registered in the plugin system

This comment was automatically added by DevBird. You can disable this feature in DevBird Settings.

AI will fix the CI (until it passes)